@justinpersaud Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Reviewer Checklist

• I have verified the author checklist is complete (all boxes are checked off).
• I verified the correct issue is linked in the ### Fixed Issues section above
• I verified testing steps are clear and they cover the changes made in this PR
  • I verified the steps for local testing are in the Tests section
  • I verified the steps for Staging and/or Production testing are in the QA steps section
  • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
• I checked that screenshots or videos are included for tests on all platforms
• I included screenshots or videos for tests on all platforms
• I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
• I verified tests pass on all platforms & I tested again on:
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
• I verified proper code patterns were followed (see Reviewing the code)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I verified that this PR follows the guidelines as stated in the Review Guidelines
• I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
• If a new component is created I verified that:
  • A similar component doesn't exist in the codebase
  • All props are defined accurately
  • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
  • The only data being stored in the state is data necessary for rendering and nothing else
  • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
• I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

🚧 chuckdries has triggered a test Expensify/App build. You can view the workflow run here.

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #96429.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-6b625206bbe-ff7e47f-595a43f53c3903693c368067d006d3e03e1f1ab7/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-6b62520-ff7e47f-638ae4f4b23e866f4ba3e1fe2804572619e6ee1f/index.html

Web 🕸️
https://96429.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

QA PASS in staging 👍

🚀 Cherry-picked to staging by https://github.com/jasperhuangg in version: 9.4.36-4 🚀

🤖 No help site changes required.

This PR updates EXPENSIFY_UK_EU_SUPPORTED_COUNTRIES to: Belgium, Denmark, Spain, Finland, Ireland, Lithuania, Luxembourg, Latvia, Netherlands, Poland, Sweden, United Kingdom, Gibraltar.

The relevant help article — Set up and manage the Expensify Card in the UK and EU, under Where the Expensify Card is supported — already lists exactly these 13 countries (plus the separate United States note). It matches the new code list one-for-one, and none of the removed countries (Cyprus, Estonia, Germany, Greece, Malta, Portugal, Slovakia, Slovenia) appear anywhere in docs/articles.

Since the help site is already accurate, I did not create a draft PR.

chuckdries, please confirm this assessment is correct — that the help article already reflects the current supported-countries list. If you believe additional docs (e.g. a different article or a country-specifics section) need updating, let me know and I'll open a draft PR.

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.4.37-0 🚀

Bundle Size Analysis (Sentry):

• Android

🚀 Cherry-picked to staging by https://github.com/roryabraham in version: 9.4.38-0 🚀

🤖 I reviewed this change against the help site files under App/docs/articles — no help site changes are required.

What this PR changes: it updates EXPENSIFY_UK_EU_SUPPORTED_COUNTRIES (the list of countries shown in the Expensify Card UK/EU "connect a bank account manually" flow) to ['BE', 'DK', 'ES', 'FI', 'IE', 'LT', 'LU', 'LV', 'NL', 'PL', 'SE', 'GB', 'GI'].

Why no docs update is needed: the only help article that enumerates these countries — Set-Up-and-Manage-the-Expensify-Card-UK-EU.md — already lists exactly this set under "Where the Expensify Card is supported":

Belgium, Denmark, Finland, Gibraltar, Ireland, Latvia, Lithuania, Luxembourg, Netherlands, Poland, Spain, Sweden, United Kingdom (+ United States, via the separate US onboarding guide)

That maps 1:1 to the new country codes in this PR, so the article is already accurate. No other article under App/docs/articles lists the removed countries (Cyprus, Estonia, Germany, Greece, Malta, Portugal, Slovakia, Slovenia) in an Expensify Card context (the only hit for those names is an unrelated travel-terms glossary).

Because the docs already reflect the new behavior, I did not create a draft help site PR.

@chuckdries, please confirm the UK/EU Expensify Card help article matches the current supported-countries list. If it already looks correct, no further action is needed. If you'd like any wording adjusted, reply with @MelvinBot <your feedback> and I'll open a docs PR.

🚀 Cherry-picked to staging by https://github.com/roryabraham in version: 9.4.40-0 🚀

🤖 Help site review: no changes required.

This PR's only change is to src/CONST/index.ts, updating EXPENSIFY_UK_EU_SUPPORTED_COUNTRIES to ['BE', 'DK', 'ES', 'FI', 'IE', 'LT', 'LU', 'LV', 'NL', 'PL', 'SE', 'GB', 'GI'].

The help site article that documents this list — Set-Up-and-Manage-the-Expensify-Card-UK-EU.md — already lists exactly these 13 countries, so it's already in sync with the updated code:

Belgium, Denmark, Finland, Gibraltar, Ireland, Latvia, Lithuania, Luxembourg, Netherlands, Poland, Spain, Sweden, United Kingdom.

No draft PR was created since no help site update is needed.

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.4.40-0 🚀

Bundle Size Analysis (Sentry):

• Android

🚀 Cherry-picked to staging by https://github.com/roryabraham in version: 9.4.41-0 🚀

🤖 Confirmed again: no help site changes are required — so there's no draft PR to open.

I re-checked the full help site, not just the country bullet list:

• The only article that enumerates these countries — Set-Up-and-Manage-the-Expensify-Card-UK-EU.md already lists exactly the 13 countries in the updated EXPENSIFY_UK_EU_SUPPORTED_COUNTRIES array (Belgium, Denmark, Finland, Gibraltar, Ireland, Latvia, Lithuania, Luxembourg, Netherlands, Poland, Spain, Sweden, United Kingdom — plus a US cross-reference note).
• No other article (wallet-and-payments, bank-accounts-and-payments, global reimbursement, etc.) contains a stale list — I grepped for every removed country (Cyprus, Estonia, Germany, Greece, Malta, Portugal, Slovakia, Slovenia) and found no card/bank references (only an unrelated Schengen-visa glossary entry in a travel article).

Because the docs already match the shipped code, a draft PR would contain no changes, so I'm not opening one.

If you believe a specific country, section, or wording in the article is wrong, reply with the exact discrepancy (e.g. "the article is missing X" or "it still shows Y") and I'll open the docs PR for that change.

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.4.41-4 🚀

Bundle Size Analysis (Sentry):

• Android